Skip to content

Doc: Add 3.3 release notes - #1509

Open
roosterfish wants to merge 3 commits into
canonical:mainfrom
roosterfish:release_notes_3.3
Open

Doc: Add 3.3 release notes#1509
roosterfish wants to merge 3 commits into
canonical:mainfrom
roosterfish:release_notes_3.3

Conversation

@roosterfish

Copy link
Copy Markdown
Contributor

This PR adds the 3.3 release notes.

@roosterfish
roosterfish requested a lite review from Copilot August 19, 2026 09:47
@github-actions github-actions Bot added the Documentation Documentation needs updating label Aug 19, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds the MicroCloud 3.3 release notes to the documentation set and links them from the release notes index so they appear in the published docs.

Changes:

  • Introduces a new “MicroCloud 3.3 release notes” page with highlights, bug fixes, and upgrade guidance.
  • Adds a new toctree entry so the 3.3 release notes are discoverable from the release notes index.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
doc/reference/release-notes/release-notes-3.3md Adds the new 3.3 release notes content (highlights, bug fixes, upgrade notes, changelog link).
doc/reference/release-notes/index.md Adds a toctree entry for the new 3.3 release notes page.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread doc/reference/release-notes/index.md
Comment thread doc/reference/release-notes/release-notes-3.3md Outdated
Comment thread doc/reference/release-notes/release-notes-3.3md Outdated
@roosterfish
roosterfish force-pushed the release_notes_3.3 branch 2 times, most recently from f015536 to d1e509e Compare August 19, 2026 10:22
@roosterfish
roosterfish marked this pull request as ready for review August 19, 2026 11:26
@roosterfish
roosterfish requested review from a team and elijahgreenstein August 19, 2026 11:26
simondeziel
simondeziel previously approved these changes Aug 19, 2026

@elijahgreenstein elijahgreenstein left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few comments.

Also, generally, the use of "got" for passive voice stands out to me as a bit too casual/informal for documentation. Using "was" or "were" would probably be preferred.

Comment thread doc/reference/release-notes/release-notes-3.3.md Outdated
Comment thread doc/reference/release-notes/release-notes-3.3.md Outdated
Comment thread doc/reference/release-notes/release-notes-3.3.md Outdated
Comment thread doc/reference/release-notes/release-notes-3.3.md Outdated
Comment thread doc/reference/release-notes/release-notes-3.3.md Outdated
Comment thread doc/reference/release-notes/release-notes-3.3.md Outdated
Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>

@simondeziel simondeziel left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@elijahgreenstein elijahgreenstein left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other than a small code-formatting issue, this looks good to me. Approving for now, and leaving it to you, @roosterfish , whether or not to put the command in a code block.

For each MicroCloud cluster you can enable the tunnel to be opened up with the already configured cluster manager.
By default the tunnel is deactivated. You can activate it with:

`microcloud cluster-manager set reverse_tunnel true`

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpicking, but since this is in a separate paragraph, rather than in-line, shouldn't it be in a code block?

Suggested change
`microcloud cluster-manager set reverse_tunnel true`
```bash
microcloud cluster-manager set reverse_tunnel true
```

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation Documentation needs updating

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants